-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Store BLSVerificationVector on disk using basic bls scheme #5480
Conversation
## Issue being fixed or feature implemented Grabbed this from #5480. ## What was done? Cleans quorum data from evoDB for old quorums. ## How Has This Been Tested? ## Breaking Changes ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_ Co-authored-by: UdjinM6 <[email protected]>
This pull request has conflicts, please rebase. |
900d0f7
to
0dc1e70
Compare
0dc1e70
to
c96addf
Compare
c96addf
to
1302beb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utACK
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utACK for squash merge
a4142f0
1302beb
to
a4142f0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
a4142f0
to
9ba595e
Compare
Had to rebase on Actual changes brought by the applied suggestion https://github.com/dashpay/dash/compare/1302beb1c80238c1136986113d9a3bd6179af0b9..a4142f0d44a5191194d036ebfb36507451d54fe7 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utACK for squash merge
Issue being fixed or feature implemented
Shouldn't change the way data is stored on mainnet/testnet nodes since they use basic bls scheme anyway now. For devnets/regtest (which activate v19 again and again) this patch should fix potential issues reading pre-fork data right after the fork.
What was done?
Pls see individual commits
How Has This Been Tested?
Run tests, run a node on testnet
Breaking Changes
n/a
Checklist: